Hello, it turns out the password / secrets I post was bad, and I fixed that with my secrete/password. now the validation is 21007 from buy and 0 by sandbox, thank you very much. however, I'm still getting rejection, rejection... and rejection by app review team, can you please kindly check this out and see if anything you can do? my other post in the forum

We are stuck with Guideline 2.1 for months as well, our app is none-consumable. so not entirely similar to Chend. After weeks of struggling, we've noticed that one significant difference of App Review and Testlfight, local Xcode testing. The receipt is not there. (or maybe a very long delay after our refreshRequest() which time-out our App). When our app load receipt in Xcode/Storkit, the receipt will be around 2K, which is malformed when validated against sandbox or buy(production). When app loads receipt in TestFlight, the receipt will be 6K, which is 21007 from buy and 0 from sandbox. Our app can handle that We still stuck with the review, main reason, the app now will time out and prompt "no receipt" when absence. If that's not good enough, let us know how we should improve. the review team keep post "Guideline 2.1" as their "reason" for rejection... that does not help much.... If receipt absence or delay matters, , the Xcode/storkit should help us test that first before this endless dance between our dev and review team. and provide clear and crisp guideline how we should handle the receipt delay or absence!! We have to figure out that the absence or delay by adding more logics into the App to defend against it by ourselves. Review team just post the guideline, and they might even think we have not do any receipt validation. We did using cloud functions. Still stuck here, our app has not been released! We appreciate all the great work that Xcode storkit team deliver to make in-app purchase development and testing so much easier. Maybe we are spoiled by that, but the receipt validation part is something that frustrates our developers and stalling our business..... Hope someone can see this and at least make the review process more friendly so we can move this forward, still waiting and haven't see the light at the end of the tunnel yet. fingers crossed...

I've got the same error message and it really point me to nowhere but fogs. I've start my projects on SWIFU UI and there are a lot of codes in it but now I can't move on since my projects won't compile and I am not sure why... this is very counter-productive, hence frustrating.